Hi, Im sorry if I accidentally ignored your coredump post. You notice that this post is from 2018 and that there is no added value in solving this issue anymore right? Now, let me start by mentioning it is never okay for the controller to present a coredump and they should be avoided at all costs. The issue with these coredumps is that they can have a variety of reasons, and that debugging them takes a lot of effort, as I need to know the exact firmware version used (incl development board version), the coredump parameters (top section) and it is very useful to see the python code and learn about its workings and when it breaks (if it breaks at the same location every time). Even then, it is still a wild goose chase. There can be many reasons for a coredump (including inadequate power supply, incorrect use of threading, firmware errors etc.) What we can do, is provide you with better tools to research the coredump and I will be working on that. Note that I have already started a documentation page here: https://docs.pycom.io/advance/coredump/, but I want to do better. Please let me know how we can improve the situation! Best, Gijs